The modem strings are in the "bbsconfig" file under "modems".
The file format is like this (comments are NOT in the file so DO NOT include them):
2400,1,0 - Maximum baud your modem has (30 chars max) LINE 1
(,) 0=No carrier detect HARDWARE cable used
1=Detect Carrier with cable (HIGHLY RECOMENDED)
The ,0 will be for using DTR hang up when it's available.
ATE0V0M1S0=0S2=2 - Modem string (up to 250 characters allowed here)
2400,1,0 - Maximum baud your modem has (30 chars max) LINE 2
ATE0V0M1S0=0S2=2 - Modem string (up to 250 characters allowed here)
And so on for each line....
The S2=2 is standard Hayes for making the "+++" into ASCII code 2. The V0 means we want numeric result codes only. You may have to tell your modem to send NO EXTENDED RESULT CODES if it's a 9600 MNP type. You need to READ your modem's manual. There's some other text in this archive about modems and strings.
The "serial" module doesn't handle hardware handshaking, so you would have to have new serial module to handle 19200 type modems correctly. I'm sure someone will have one soon. It would be nice to have a much more configurable one.
The "modems" module handles all the modem string stuff, and other modules may be available later that handle special modems.
I HIGHLY RECOMMEND GETTING A CARRIER DETECT MODEM CABLE !! This is a standard modem cable most of the time. If you're not sure, use a "ohm" meter and check your pins against the "modem cable" file.
WHY CARRIER DETECT ? Because your thousands of users will keep getting BUSY signals while your BBS waits to TIME OUT !!! Now picture this:
You are NOT running a carrier detect cable, a user hangs up on your system, someone else calls the BBS (with their AUTODIAL on just to make things worse) and the modem then sends the "ring" to the serial port. GUESS WHAT THE BBS THINKS ??? It thinks a user is STILL TYPING ! (so it NEVER hangs up for HOURS !)
Please, please, please run a proper cable. If you have CHECKED your cable and it's sending back carrier detect for sure, there may be some sort of Mac hardware change that prevents the "serial" module from detecting carrier detect. IT'S MOST LIKELY YOUR MODEM STRINGS ! Some modems need &C1 or C1 in the string in order to send back carrier detect.
If you are really having problems, look for other "serial" modules on the support BBS and see if others are having the same problems. ALL serial I/O is handled through a REPLACEABLE module !
The BBS can use BOTH ports if you want it to. It WILL not access any special serial cards till someone writes a "serial" module to handle them.
You can select "Modems to Ring" from the pull down menu, it will SHUT the modems up if you don't have the cables hooked to anything. (it skips to wait for a ring)
If you are UNSURE of your strings, and as a TEMPORARY measure, take out the &C0 or just C0 and the M1 (speaker setting) so that you have only the basics for your modem. Then put in 1200,0,0 in the first line so that you are running at 1200 baud with NO hardware carrier detect. This should let you at least get the BBS running, then you can play with it ADDING ONE THING AT A TIME till you figure out what's going on.
